from
Clause 5.3.2 is written into a circular buffer of length 
for the
-th
coded block,
where 
is
defined in Clause 5.3.2.Please refer to RP-202044 for detailed scope of the RAN4-led WI, particularly the details to specify high order modulation for PDSCH.
R1-2007617 On support of DL 1024QAM for NR FR1 Huawei, HiSilicon
R1-2007700 On supporting DL 1024QAM for NR FR1 vivo
R1-2007846 DL 1024QAM for NR FR1 CATT
R1-2007977 Discussion on DL 1024QAM for NR FR1 ZTE
R1-2008201 Discussion on DL 1024QAM for NR FR1 Samsung
R1-2009009 Support of 1024QAM Intel Corporation
R1-2009171 Work plan on supporting 1024 QAM Rapporteurs (Nokia, Ericsson)
R1-2009172 Considerations for NR DL 1024 QAM in FR1 Nokia, Nokia Shanghai Bell
R1-2009209 1024QAM for NR DL Ericsson
R1-2009282 Introduction of 1024-QAM modulation for NR PDSCH Qualcomm Incorporated
[103-e-NR-1024QAM-01] – Ajit (Ericsson)
Email discussion/approval for DL 1024QAM
R1-2009799 Summary of Email discussion [103-e-NR-1024QAM-01] Moderator (Ericsson)
Decision: As per email decision posted on Nov.6th,
Agreements:
· Introduce new RRC signaling to indicate use of 1024-QAM CQI table.
· For supporting 1024-QAM in NR downlink, adopt the LTE 1024-QAM constellation.
· 1024-QAM MCS table can be used only with DCI format with CRC scrambled by C-RNTI or CS-RNTI.
Decision: As per email decision posted on Nov.11th,
Agreements:
· Introduce new RRC signaling to indicate use of 1024-QAM MCS table for at least DCI format 1_1
o FFS : support of 1024-QAM MCS table for DCI format 1_2
§ Note: If 1024-QAM MCS table for DCI format 1_2 is supported, separate RRC signaling is used for each of the two DCI formats 1_1 and 1_2, respectively
o FFS : whether the RRC signaling is only introduced in PDSCH-Config or it can also be separately configured in SPS-Config
Decision: As per email decision posted on Nov.13th,
Note: All below endorsed TPs are only for reference. No Rel-17 specs to be created at this early stage of the WI.
Agreements:
· RRC signaling (mcs-Table-r17) to indicate use of 1024-QAM MCS table for DCI format 1_1 is present only in PDSCH-config
· When UE is configured with mcs-Table-r17 set to ‘qam1024’ in PDSCH-Config,
o UE uses 1024-QAM MCS table for PDSCH scheduled with a DCI format 1_1 with CRC scrambled by C-RNTI,
o UE uses 1024-QAM MCS table for PDSCH scheduled with the DCI format 1_1 with CRC scrambled by CS-RNTI if the UE is not configured with mcs-Table in SPS-Config
· Note: If 1024-QAM MCS table for DCI format 1_2 is supported, similar approach is used for 1024-QAM MCS table usage with DCI format 1_2
Agreements:
Adopt following TP for in 38.212, subclause 5.4.2.1 for TBS_LBRM determination.
-------- Start of TP --------
5.4.2.1 Bit selection
The
bit sequence after encoding from
Clause 5.3.2 is written into a circular buffer of length for the
-th
coded block,
where is
defined in Clause 5.3.2.
For the -th code
block,
let 
if 
and 
otherwise,
where
, 
, 
is
determined according to Clause 6.1.4.2 in [6, TS 38.214] for UL-SCH and Clause
5.1.3.2 in [6, TS 38.214] for DL-SCH/PCH, assuming the following:
- maximum number of layers for one TB for UL-SCH is given by X, where
o elseif the higher layer parameter maxRank of pusch-Config of the serving cell is configured, X is given by the maximum value of maxRank across all BWPs of the serving cell
o otherwise, X is given by the maximum number of layers for PUSCH supported by the UE for the serving cell
- maximum number of layers for one TB for DL-SCH/PCH is given by the minimum of X and 4, where
o if the higher layer parameter maxMIMO-Layers of PDSCH-ServingCellConfig of the serving cell is configured, X is given by that parameter
o otherwise, X is given by the maximum number of layers for PDSCH supported by the UE for the serving cell
-
if the higher layer parameter mcs-Table-r17 given by a pdsch-Config
for at least one DL BWP of the serving cell is set to 'qam1024', maximum
modulation order 
is assumed for DL-SCH, elseif the higher layer parameter mcs-Table
given by a pdsch-Config for at least one DL BWP of the serving cell is
set to 'qam256', maximum modulation order 
is assumed for DL-SCH; otherwise else a
maximum modulation order 
is assumed for DL-SCH;
Unchanged parts are omitted
-------- End of TP --------
Agreements:
· Adopt following text proposal for TS 38.201, subclause 4.2.2.
-------- Start of TP --------
4.2.2 Physical channels and modulation
Unchanged parts are omitted
The modulation schemes supported are
-
in
the downlink, QPSK, 16QAM, 64QAM, and
256QAM and 1024 QAM
- in the uplink, QPSK, 16QAM, 64QAM and 256QAM for OFDM with a CP and π/2-BPSK, QPSK, 16QAM, 64QAM and 256QAM for DFT-s-OFDM with a CP
Unchanged parts are omitted
-------- End of TP --------
Agreements:
· Adopt following TP for 38.211 to reflect the agreed 1024-QAM constellation.
-------- Start of TP --------
Unchanged parts are omitted
5.1.7 1024QAM
In case
of 1024QAM modulation, 10-tuplets of bits, 
, are mapped to complex-valued modulation symbols 
according to
-------- End of TP --------
Agreements:
- Adopt following TP to 38.211, subclause 7.3.1.2, to reflect 1024-QAM support for PDSCH
Table 7.3.1.2-1: Supported modulation schemes.
|
Modulation scheme |
Modulation order |
|
QPSK |
2 |
|
16QAM |
4 |
|
64QAM |
6 |
|
256QAM |
8 |
|
1024QAM |
10 |
Agreements:
· Adopt following TP for 38.214, subclause 5.2.2.1, reflecting the 1024-QAM CQI table usage based on corresponding RRC parameter as follows.
o Note : RAN1 to further align with the RAN2 signaling design
-------- Start of TP --------
5.2.2.1 Channel quality indicator (CQI)
Unchanged parts are omitted
The CQI indices and their interpretations are given in Table 5.2.2.1-2 or Table 5.2.2.1-4 for reporting CQI based on QPSK, 16QAM and 64QAM. The CQI indices and their interpretations are given in Table 5.2.2.1-3 for reporting CQI based on QPSK, 16QAM, 64QAM and 256QAM. The CQI indices and their interpretations are given in Table 5.2.2.1-5 for reporting CQI based on QPSK, 16QAM, 64QAM, 256QAM and 1024 QAM.
Based on an unrestricted observation interval in time unless specified otherwise in this Clause, and an unrestricted observation interval in frequency, the UE shall derive for each CQI value reported in uplink slot n the highest CQI index which satisfies the following condition:
- A single PDSCH transport block with a combination of modulation scheme, target code rate and transport block size corresponding to the CQI index, and occupying a group of downlink physical resource blocks termed the CSI reference resource, could be received with a transport block error probability not exceeding:
o 0.1, if the higher layer parameter cqi-Table in CSI-ReportConfig configures ‘table1’ (corresponding to Table 5.2.2.1-2), or ‘table2’ (corresponding to Table 5.2.2.1-3), or if the higher layer parameter cqi-Table-r17 in CSI-ReportConfig configures ‘table4’ (corresponding to Table 5.2.2.1-5)
o 0.00001, if the higher layer parameter cqi-Table in CSI-ReportConfig configures ‘table3’ (corresponding to Table 5.2.2.1-4).
Unchanged parts are omitted
-------- End of TP --------
Agreements:
· Companies are encouraged to use below link-level simulation assumptions for assessing at least transition point between 256-QAM and 1024-QAM.
|
Parameter |
Value |
|
Carrier frequency, SCS, System BW |
3.5GHz, 30kHz, 100 MHz |
|
Channel model |
AWGN, CDL-B or CDL-C in TR 38.901 with up to 30ns delay spread |
|
UE speed |
3km/h, 0km/h |
|
Number of UE antennas |
1T4R, |
|
Number of gNB antennas |
32T32R or 64T64R or 2T or 8T |
|
Tx EVM |
0, 2% |
|
Rx EVM |
0, 3% |
|
MCS |
256 QAM, 1024 QAM Coding Rate*: 0.70, 0.75, 0.80, 0.85, 0.90 Other coding rates are not precluded and, if simulated, to be reported by each company |
|
DMRS type |
DM-RS type 1 |
|
Number of DMRS symbols |
1 |
|
Number of scheduled RBs |
273 |
|
PDSCH mapping |
Type A, Start symbol 2, Duration 12 |
|
Rank |
Rank1, Rank 2, |
|
Channel estimation |
Realistic channel estimation |
|
Metric |
Crossover SNR at transition points between 256-QAM and 1024-QAM |
|
Note*: Coding rates are used for 1024QAM, while coding rates for 256QAM are selected from TS38.214 MCS table 2 |
|
Please refer to RP-202886 for detailed scope of the RAN4-led WI, particularly the details to specify high order modulation for PDSCH.
R1-2102200 Session notes for 8.16 (Introduction of DL 1024QAM for NR FR1) Ad-hoc Chair (Samsung)
R1-2100215 On support of DL 1024QAM for NR FR1 Huawei, HiSilicon
R1-2100369 DL 1024QAM for NR FR1 CATT
R1-2100484 On supporting DL 1024QAM for NR FR1 vivo
R1-2100532 Discussion on DL 1024QAM for NR FR1 ZTE , Sanechips
R1-2100686 Support of 1024QAM Intel Corporation
R1-2101071 Discussion on DL 1024QAM for NR FR1 CMCC
R1-2101246 On remaining issues of DL 1024QAM for NR FR1 Samsung
R1-2101421 Support for NR DL 1024 QAM in FR1 Nokia, Nokia Shanghai Bell
R1-2101496 1024-QAM for NR PDSCH Qualcomm Incorporated
R1-2101564 1024QAM for NR DL Ericsson
[104-e-NR-1024QAM-01] – Ajit (Ericsson)
Email discussion/approval for DL 1024QAM
- 1st check point: Jan 27
- 2nd check point: Feb 1
- 3rd check point: Feb 5
R1-2101823 Initial summary for introduction of 1024QAM for NR DL Moderator (Ericsson)
Decision: From GTW session on Jan 25th,
Working Assumption (to be confirmed next
week)
Agreement
Reuse LTE CQI table with 1024-QAM entries
|
CQI index |
modulation |
code rate x 1024 |
Efficiency |
|
0 |
Out of range |
||
|
1 |
QPSK |
78 |
0.1523 |
|
2 |
QPSK |
193 |
0.377 |
|
3 |
QPSK |
449 |
0.877 |
|
4 |
16QAM |
378 |
1.4766 |
|
5 |
16QAM |
616 |
2.4063 |
|
6 |
64QAM |
567 |
3.3223 |
|
7 |
64QAM |
666 |
3.9023 |
|
8 |
64QAM |
772 |
4.5234 |
|
9 |
64QAM |
873 |
5.1152 |
|
10 |
256QAM |
711 |
5.5547 |
|
11 |
256QAM |
797 |
6.2266 |
|
12 |
256QAM |
885 |
6.9141 |
|
13 |
256QAM |
948 |
7.4063 |
|
14 |
1024QAM |
853 |
8.3301 |
|
15 |
1024QAM |
948 |
9.2578 |
R1-2101892 Summary for introduction of 1024QAM for NR DL Moderator (Ericsson)
Decision: From GTW session on Jan 27th,
Agreement
For supporting 1024-QAM in NR downlink, adopt a five-bit MCS table with 1024-QAM entries:
· Remove M explicit MCS entries (from MCS indices 0-27) from the NR 256QAM MCS table and add M new entries for 1024QAM
·
(working assumption)
M=5
· Add one implicit MCS entry corresponding to 1024-QAM
·
(working assumption)
Add M-1 explicit MCS entries corresponding to 1024-QAM as follows:
|
modulation |
code rate x 1024 |
Efficiency |
|
10 |
805.5 |
7.8662 |
|
10 |
853 |
8.3301 |
|
10 |
900.5 |
8.7939 |
|
10 |
948 |
9.2578 |
R1-2101959 Summary#2 for introduction of 1024QAM for NR Moderator (Ericsson)
Decision: From GTW session on Jan 29th,
Agreement
For supporting 1024-QAM in NR downlink, remove following M (=5) MCS entries from the NR 256-QAM MCS table
· 2, 4, 6, 8, 10
Agreement
Introduce separate RRC signaling to indicate use of 1024-QAM MCS table for DCI format 1_2.
Decision: As per email decision posted on Jan 30th,
Agreement
The following text proposals are endorsed for TS38.214.
· TP in section 5 (R1-2100484) for TBS determination for subclause 5.1.3.2 of TS 38.214
· TP4 from Annex D (R1-2101564) for PT-RS determination for subclause 5.1.6.3 of TS 38.214 (with [INDEX of FIRST-16QAM ENTRY of 1024-QAM Table] be replaced with the actual value given by 3)
· TP1 from Annex D (R1-2101564) for per-cell data rate constraint for subclause 5.1.3 of TS 38.214
The above are summarized in:
R1-2102023 First Set of Agreed TPs for support of 1024QAM in NR DL Moderator(Ericsson)
R1-2102059 Summary#3 for introduction of 1024QAM for NR DL Moderator (Ericsson)
R1-2102087 Second Set of Agreed TPs for support of 1024QAM in NR DL Moderator (Ericsson)
Decision: From GTW session,
Agreement
· The text proposals in R1-2102087 are endorsed for TS38.214.
Agreement
LS to RAN2 and RAN4 to inform them of RAN1 decisions on 1024QAM and related RRC parameters, CQI/MCS tables is approved in R1-2102088.
Final summary in R1-2102089.
